TR
11111

COURSE INTRODUCTION AND APPLICATION INFORMATION

se.cs.ieu.edu.tr

Course Name
Code
Semester
Theory
(hour/week)
Application/Lab
(hour/week)
Local Credits
ECTS
Fall/Spring
Prerequisites
None
Course Language
Course Type
Elective
Course Level
-
Mode of Delivery -
Teaching Methods and Techniques of the Course Application: Experiment / Laboratory / Workshop
Course Coordinator -
Course Lecturer(s) -
Assistant(s) -
Course Objectives
Learning Outcomes The students who succeeded in this course;
  • On successful completion of this course, students will be able to:
  • Understand how a user program is executed on the multilevel structure of a computer,
  • Evaluate the relationship between hardware and software components of a computer,
  • Present hardware and software alternatives in implementing a functionality of a computer,
  • Understand how a computer instruction is transformed into a set of hardware signals,
  • Evaluate the effects of different hardware component alternatives on execution speed of a computer.
Course Description

 



Course Category

 Core Courses
Major Area Courses
X
Supportive Courses
Media and Managment Skills Courses
Transferable Skill Courses

 

WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES

Week Subjects Required Materials
1 Introduction Tanenbaum Chapter 1
2 Processors and Primary Memory Tanenbaum Sections 2.1, 2.2
3 Secondary Memory and Inputoutput Tanenbaum Sections 2.3, 2.4
4 / CPU Chips and Buses Tanenbaum Sections 3.4, 3.5, 3.6, 3.7
5 The Microarchitecture Level : Examples and Implementation Tanenbaum Sections 4.1, 4.2, 4.3
6 The Microarchitecture Level : Design and Performance Tanenbaum Sections 4.4, 4.5, 4.6, 4.7
7 Review of the Semester  
8 Midterm
9 The Instruction Set Architecture Level: Overview, Data Types and Formats Tanenbaum Sections 5.1, 5.2, 5.3
10 The Instruction Set Architecture Level: Addressing and Instruction Types Tanenbaum Sections 5.4, 5.5
11 The Instruction Set Architecture Level: Flow of Control and Examples Tanenbaum Sections 5.6, 5.7, 5.8
12 The Assembly Language Level: Instruction Format and Macros Tanenbaum Sections 7.1, 7.2
13 The Assembly Language Level: Assembly Process, Linking and Loading Tanenbaum Sections 7.3, 7.4
14 Parallel Computer Architectures Tanenbaum Chapter 8
15 Review of the Semester  
16 Review of the Semester  
Course Notes/Textbooks Structured Computer Organization, A.S. Tanenbaum, 5th ed. 2006, PrenticeHall ISBN 0131485210
Suggested Readings/Materials Computer Architecture: A Quantitative Approach, Third Edition, John L. Hennessy David A. Patterson David Goldberg, Morgan and Kaufmann

 

EVALUATION SYSTEM

Semester Activities Number Weigthing
Participation
10
Laboratory / Application
Field Work
Quizzes / Studio Critiques
6
15
Portfolio
Homework / Assignments
8
15
Presentation / Jury
Project
Seminar / Workshop
Oral Exam
Midterm
1
25
Final Exam
1
35
Total

Weighting of Semester Activities on the Final Grade
65
Weighting of End-of-Semester Activities on the Final Grade
35
Total

ECTS / WORKLOAD TABLE

Semester Activities Number Duration (Hours) Workload
Course Hours
(Including exam week: 16 x total hours)
16
2
32
Laboratory / Application Hours
(Including exam week: 16 x total hours)
16
2
Study Hours Out of Class
Field Work
Quizzes / Studio Critiques
6
3
Portfolio
Homework / Assignments
8
2
Presentation / Jury
Project
Seminar / Workshop
Oral Exam
Midterms
1
10
Final Exams
1
12
    Total
120

 

COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP

#
 Program Competencies/Outcomes
* Contribution Level
1
2
3
4
5
1 Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute X
2 Be able to design and analyze software at component, subsystem, and software architecture level X
3 Be able to develop software by coding, verifying, doing unit testing and debugging X
4 Be able to verify software by testing its behaviour, execution conditions, and expected results X
5 Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation X
6 Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically
7 To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning
 X
8 Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes X
9 Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance X
10 To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software
11 To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering
12 Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering
13

Be able to use a foreign language to follow related field publications and communicate with colleagues

*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest

 

İzmir Ekonomi Üniversitesi | Sakarya Caddesi No:156, 35330 Balçova - İZMİR Tel: +90 232 279 25 25 | webmaster@ieu.edu.tr | YBS 2010